Skip to content

fix(patch): cherry-pick 0659ad1 to release/v0.32.0-pr-21042 to patch version v0.32.0 and create version 0.32.1#21048

Merged
jacob314 merged 1 commit into
release/v0.32.0-pr-21042from
hotfix/v0.32.0/0.32.1/stable/cherry-pick-0659ad1/pr-21042
Mar 4, 2026
Merged

fix(patch): cherry-pick 0659ad1 to release/v0.32.0-pr-21042 to patch version v0.32.0 and create version 0.32.1#21048
jacob314 merged 1 commit into
release/v0.32.0-pr-21042from
hotfix/v0.32.0/0.32.1/stable/cherry-pick-0659ad1/pr-21042

Conversation

@gemini-cli-robot

Copy link
Copy Markdown
Collaborator

This PR automatically cherry-picks commit 0659ad1 to patch version v0.32.0 in the stable release to create version 0.32.1.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated cherry-pick to create a patch release 0.32.1 for the v0.32.0 stable version. The primary change involves modifying the priority of the global keypress handler in the AppContainer component, likely to resolve an interaction issue or improve responsiveness. Corresponding tests for expansion persistence, which might have been affected by this change or deemed no longer relevant, have been removed.

Highlights

  • Keypress Handling Priority Adjustment: The global keypress handler in AppContainer now operates with a higher priority, changing from KeypressPriority.Low to true. This ensures it takes precedence over other keypress listeners.
  • Removed Expansion Persistence Tests: A suite of tests related to the Expansion Persistence feature within AppContainer.test.tsx has been removed. These tests covered scenarios like resetting expansion on unhandled keys and toggling expansion with Ctrl+O.
Changelog
  • packages/cli/src/ui/AppContainer.test.tsx
    • Removed the Expansion Persistence test suite.
  • packages/cli/src/ui/AppContainer.tsx
    • Updated the useKeypress hook for handleGlobalKeypress to use priority: true instead of KeypressPriority.Low.
Activity
  • This pull request was automatically generated as a cherry-pick to create a patch release. No human activity has been recorded.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request cherry-picks a change that aims to fix an issue with the UI's expansion state. The change involves increasing the priority of a global keypress handler and removing the corresponding test suite for expansion persistence. While the intent seems to be to prevent the UI from collapsing unexpectedly, the change to the handler's priority does not address the root cause of the issue, which is a logical flaw in handleGlobalKeypress. This can still lead to a poor user experience, violating consistency with existing UI behavior. Furthermore, removing the entire test suite for this feature is concerning as it increases the risk of regressions. I've added specific comments with suggestions to address these points.

});
});

describe('Expansion Persistence', () => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This test suite for 'Expansion Persistence' has been removed. These tests were valuable for ensuring the view expansion/collapse behavior is correct and predictable. For instance, they verified that the view collapses only on unhandled keypresses. Given the potential for bugs in this area, removing these tests is risky. It would be better to update them to match the desired behavior rather than deleting them entirely. Without these tests, regressions in this area are more likely to occur.

isActive: true,
priority: KeypressPriority.Low,
});
useKeypress(handleGlobalKeypress, { isActive: true, priority: true });

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Changing the priority to High here appears to be an indirect attempt to fix an issue with the view collapsing unexpectedly. However, the root cause is a logical flaw within the handleGlobalKeypress handler itself, which this priority change does not address. The handler collapses the view on any keypress when it's expanded, which is likely not the intended behavior. This can lead to a poor user experience, for example, collapsing the view while the user is typing. A more direct fix within handleGlobalKeypress is recommended to ensure the view only collapses intentionally.

References
  1. Maintain consistency with existing UI behavior across components. Defer non-standard UX pattern improvements to be addressed holistically rather than in a single component. The current behavior of collapsing the view on any keypress deviates from expected UI patterns and creates a poor user experience.

@github-actions

github-actions Bot commented Mar 4, 2026

Copy link
Copy Markdown

Size Change: -22 B (0%)

Total Size: 25.8 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 25.3 MB -22 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js 221 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js 227 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js 11.5 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js 132 B 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B
./bundle/sandbox-macos-strict-open.sb 4.82 kB 0 B
./bundle/sandbox-macos-strict-proxied.sb 5.02 kB 0 B

compressed-size-action

@jacob314 jacob314 merged commit e8a57c7 into release/v0.32.0-pr-21042 Mar 4, 2026
27 of 28 checks passed
@jacob314 jacob314 deleted the hotfix/v0.32.0/0.32.1/stable/cherry-pick-0659ad1/pr-21042 branch March 4, 2026 02:37
@sripasg sripasg added the size/m A medium sized PR label Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/m A medium sized PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants